Repository navigation
Prepare native fired-timer redrive and fractional-clock guidance - #541
Conversation
|
Bounded producer-semantic review PASS for the two English deltas at exact The API reference matches accepted Server Clock authority and precision are correct. Consumed steps use their original event times, the initial anchor uses persisted run start, repeated redrive preserves existing clock strings, and historical lost fractions cannot be reconstructed. This does not add ordinary-entry clock support or assert a new SDK release is needed. I also checked the historical native claim against exact published tags The pending-publication callout and unchanged selected pair correctly distinguish source acceptance from an actual qualified producer/SDK/Chart tuple. Complete PR file inventory is only these two English documents, so selectors, installers, OpenAPI and catalog are unchanged by this head. This is source prose review; translation, final producer/Chart receipt binding, build/deployment and live readback remain later gates. No installed or cross-mode acceptance is inherited. |
|
Bounded English status-clause review at Please distinguish the published immutable producer from pending stable adoption/consumer qualification. The selected 3.10/Chart 2.0 tuple remains unchanged. This correction requests no publication, runtime or promotion action and does not lift any existing hold. |
…w-github-io/native-timer-redrive
|
Fixed the producer's status-wording finding in The timer/refusal/clock contract and all executable examples remain unchanged. All14 source hashes, localized code tokens and link targets agree with the corrected English. The selected3.10/Chart2.0 pair and static artifact bytes remain identical to current main. The branch also includes current main via normal merge. Re-review of the status distinction and current CI are pending; no runtime, publication or promotion gate is lifted. |
|
Python ordinary source/locale review for exact In The remaining bounded review passes: I compared all seven localized timer/refusal/clock sections with English, checked the first-use full-instant/later inherited-string distinction, persisted run-start authority, original history, fresh shared timer identity, unchanged callback/timer-work conditions and the explicit ordinary-entry/refusal limits. The new callouts distinguish published/qualified immutable 3.11 from stable promotion, final Release/Chart adoption and actual installed SDK evidence, consistently with Server1218/6868218894. Mechanical checks on the frozen Git objects confirm all 14 source-hash entries match the two current English files, only those two entries change in each locale hash manifest, all seven added sections preserve the English inline contract-token and link multisets, and all code fences in the 16 changed guides are byte-identical to current base This review executed only Git reads and text/hash checks. It ran no site build, SDK, Worker, Server or installed clock cell, and does not clear the separate physical-row/consumer/promotion holds. After the single wording correction and refreshed source hash, I can rebind to the exact successor. |
|
Bounded English status-clause re-review: PASS at This verdict covers those English native status clauses only. It does not review unrelated main/locale changes, establish installed SDK acceptance, select an artifact or lift promotion/adoption holds. Ordinary exact-head review/check/build/Pages and public follow-through remain the Docs delivery gates. |
|
The bounded English status PASS 6876882703 retains its scope at |
|
Python ordinary source/locale review: PASS for exact The Chinese callout now explicitly says stable promotion, final Release, Chart adoption and the relevant installed-consumer verification remain pending. The analogous Ukrainian sentence also clearly says awaiting completion. I verified that these are the only two changed files/sentences relative to The complete seven-locale timer/refusal/clock review and 23-path scope from the prior review therefore carry forward. Published/qualified immutable 3.11 is correctly separated from selected stable behavior and the still-pending consumer/promotion/Chart work. The changed guide does not establish an installed Python clock result or clear the separate physical-row criterion. Verification was limited to exact Git-object diffs and text/hash checks. I ran no site build, SDK, Worker, Server or clock cell. Server's producer disposition, current CI, normal integration and any eventual Pages/public readback remain independently required. |
|
Final source validation is complete for Both English guides and all seven translations are complete. The final all-eight-locale build and rendered checks of all 16 affected pages pass. All 11 current-head checks pass. The producer rebind and independent source/locale review have no remaining findings. The status wording now correctly distinguishes the published, qualified immutable 3.11 producer from pending stable adoption. This remains a draft. Publication/adoption awaits the applicable PHP/Python/Rust full-precision cold-worker receipts and remaining stable-alias, final Release and Chart gates. The selected Server 3.10.0 / Chart 2.0.0 pair and machine artifacts are unchanged. This result closes the outstanding documentation source/review/check work; it does not claim public delivery or lift the separate release and installed-consumer requirements. |
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Native Server 3.11.0 is the released source of plain fired-timer redrive and full-precision replay clocks. Replace the pending-adoption callout with a release note, record the passing installed Rust 4.18.0, Python 2.17.2 and PHP 3.18.3 cold-worker receipts on server#980, note the server's millisecond clock storage, and say in failures/recovery what 3.11.0 adds over 3.8.0-3.10.x. Apply the same changes in all seven locales and rebind their reviewed source hashes for the two pages. Co-Authored-By: Claude Opus 5.5 <[email protected]>
|



Prepare bounded Service Mode guidance for native plain-timer redrive and fractional replay clocks. The API reference covers the ordered timer pair, fresh shared successor ID, no new timer row/task, original clock strings and immediate-predecessor lineage across repeated redrive, persisted initial/event clock authorities and historical rounding. Failures/recovery preserves the published 3.8–3.10 limitations and links the behavior added in native Server 3.11.0.
Both English guides and all seven localized versions are complete, with 14 reviewed-source bindings and unchanged executable examples. Current head 87b0b98 merges current main and updates both guides in all eight languages for the 3.11.0 release. Locally at that head,
npm test, the public-boundary checks and the full all-eight-localenpm run buildpass, including the translation/source-hash, changed-guide and localized-link checks.Native Server 3.11.0 is released, and the stable
3/latestaliases point to it. Installed published-SDK cold-worker redrive receipts passed against 3.11.0 for Rust SDK 4.18.0, Python SDK 2.17.2 and PHP SDK 3.18.3 (server#980). The API reference callout now says the behavior is available from 3.11.0. Failures/recovery keeps the 3.8.0–3.10.x limits and adds what 3.11.0 changes. The server stores these clocks at millisecond precision. The bounded timer/clock semantics are unchanged.Core's #992 precision/reference work stays separate. The site's stable-release manifest, installers and protocol/catalog files are unchanged relative to current main; selecting Server 3.11.0/Chart 2.1.0 there is outside this PR. No runtime, promotion or separate #534/Workflow1130 operation is selected by this PR.